IBM Books

Network Utility User's Guide


Chapter 17. DLSw Example Configuration Details

This chapter contains diagrams and configuration parameter tables for several of the example DLSw network configurations in Chapter 16, "Data Link Switching". The parameter values shown are from real working test configurations.

For an explanation of the columns and conventions in the configuration parameter tables, see Example Configuration Table Conventions.

The Network Utility World Wide Web pages contain binary configuration files that match these configuration parameter tables. To access these files, follow the Download link from:

http://www.networking.ibm.com/networkutility

The configurations documented in this chapter are:

Table 17-1. Cross-Reference of Example Configuration Information

Configuration Description Parameter Table
DLSw LAN Catcher Table 17-2
DLSw LAN Channel Gateway Table 17-3

Figure 17-1. DLSw LAN Catcher

View figure.

Table 17-2. DLSw LAN Catcher

See page "DLSw LAN Catcher" for a description and Figure 17-1 for a diagram of this configuration.

Configuration Program Navigation


Configuration Program Values


Command-Line Commands


Notes


Devices
Adapters
Slots


Slot 1: 2-Port TR


See "add device" on next row


1


Devices
Adapters
Ports


Slot 1/Port 1: Interface 0: TR
Slot 1/Port 2: Interface 1: TR

Config>add dev tok

(once per port)


2


Devices
Interfaces


Interface 0
MAC address: 400022AA0001
Packet size: 4399
Interface 1
MAC address: 400022AA0002
Packet size: 4399

Config>net 0
TKR config>set phy 40:00:22:AA:00:01
TKR config>packet 4399
TKR config>exit
Config>net 1
TKR config>set phy 40:00:22:AA:00:02
TKR config>packet 4399



System
General


System name: NU_A
Location: XYZ
Contact: Administrator

Config>set host
Config>set location
Config>set contact




System
SNMP Config
General


SNMP (checked)

Config>p snmp
SNMP Config>enable snmp



System
SNMP Config
Communities
General


Community name: admin
Access type: Read-write trap
Community view: All

SNMP Config>add community
SNMP Config>set comm access write


3


Protocols
IP
General


Internal address: 172.128.252.1
Router ID: 172.128.1.1

Config>p ip
IP config>set internal
IP config>set router-id



Protocols
IP
Interfaces


Interface 0 (TR slot 1 port 1)
IP address: 172.128.1.1
Subnet mask: 255.255.255.0
Interface 1 (TR slot 1 port 2)
IP address: 172.128.2.1
Subnet mask: 255.255.255.0

IP config>add address

(once per i/f)


4


Protocols
IP
OSPF
General


OSPF (checked)

Config>p ospf
OSPF Config>enable ospf


5


Protocols
IP
OSPF
Area Configuration
General


Area number: 0.0.0.0
Stub area (not checked)

OSPF Config>set area



Protocols
IP
OSPF
Interfaces


Interface 0
OSPF (checked)
Interface 1
OSPF (checked)

OSPF Config> set interface
  Interface IP address  172.128.1.1
  Attaches to area 0.0.0.0

(Accept other defaults)

OSPF Config>set interface
  Interface IP address  172.128.2.1
  Attaches to area 0.0.0.0

(Accept other defaults)



Protocols
DLSw
General
General


DLSw (checked)
SRB segment: FFD
Forward explorers: disabled

Config>p dls
DLSw Config>enable dls
DLSw Config>set srb
DLSw Config>disable forward all


6


Protocols
DLSw
General
Dynamic Neighbors


Dynamic neighbors (checked)

DLSw Config>enable dynamic


7


Protocols
DLSw
Interfaces


Interface 0 (TR slot 1 port 1)
SAP type: SNA (SAPs 0,4,8,C)

DLSw Config>open 0 sna


8


Protocols
Bridging
General


Bridging (checked)
DLSw (checked)

Config>p asrt
ASRT config>enable br
ASRT config>enable dls


9


Protocols
Bridging
Interfaces


Interface 0 (TR slot 1 port 1)
Bridging port (checked)
Interface supports: SRB
Segment number: 001
MTU size: 4399


('enable br' assumed)
ASRT config>disable transp 1
ASRT config>enable source 1
ASRT config>delete port 2


10

Notes:

  1. add dev defines a single port, not an adapter.

  2. The configuration program assigns an interface number to all ports of an adapter automatically and you delete the ones you do not want to use. From the command line, you type the add dev command for each port you want to use, and the interface number (also known as "net number") is the output of the command.

  3. You need a write-capable SNMP community only if you want to download configuration files from the configuration program directly into the router. SNMP is not required to TFTP a configuration file to the router.

  4. Only Interface 1 needs to be configured for IP for DLSw to function correctly in this example. Interface 0 is configured here for IP, solely for box management purposes.

  5. You can also use RIP in place of OSPF.

  6. We disable the forwarding of remote explorers as a general filter, to prevent backbone LAN traffic from generating DLSw search messages on the WAN links to remote sites. This means that all circuits must be initiated by the remote routers. If your network requires the host to be able to initiate connections out to the remote sites, change this parameter to "forward to all DLSw peers".

    If the remote routers are IBM routers, you can configure them individually to control which search messages they want to receive, using MAC address and NetBIOS name lists. You can also configure whether each will bring up its TCP connection to Network Utility all the time or drop it when unused, using the connectivity setup type parameter.

  7. Having dynamic neighbors enabled is the default value, so you do not have to change this panel or issue this command. We show it here to point out that this is the parameter that allows remote DLSw partners (neighbors) to establish TCP connections to this Network Utility without you having to define their IP addresses here. Each remote router needs to be configured with this Network Utility's internal IP address (172.128.252.1) as its partner address.

  8. SAPs do not need to be opened on Interface 1 since that interface is only carrying IP traffic and not LLC traffic.

  9. "enable br" automatically creates TB bridge ports for both token-ring interfaces. Bridge port numbers are 1 and 2, and are independent of adapter port numbers.

  10. The disable and enable commands change bridge port 1 from TB to SRB. The "delete port" command turns off bridging on interface 1 (bridge port 2). Bridging would be required on this interface if we needed to support local end station traffic bridging from the Campus Backbone to the host.

Figure 17-2. DLSw LAN Gateway

View figure.

Table 17-3. DLSw LAN Gateway

See page "DLSw LAN Channel Gateway" for a description and Figure 17-2 for a diagram of this configuration.

Configuration Program Navigation


Configuration Program Values


Command-Line Commands


Notes


Devices
Adapters
Slots


Slot 1: 2-Port TR
Slot 2: ESCON


See "add device" on next row


1


Devices
Adapters
Ports


Slot 1/Port 1: Interface 0: TR
Slot 2/Port 1: Interface 1: ESCON

Config>add dev tok
Config>add dev escon


2


Devices
Interfaces


Interface 0
MAC address: 400022AA0001

Config>net 0
TKR config>set phy 40:00:22:AA:00:01



Devices
Channel Adapters
ESCON Interfaces
ESCON Interfaces


Base network number: 1
Protocol type: LSA (do this first)
Loopback (checked - do this second)
LAN type: Token Ring
Maximum data frame: 2052
MAC address: 400022AA0099

Config>net 1
ESCON Config>add lsa 
(added as interface 2)
ESCON Add Virtual>enable loopback
ESCON Add Virtual>mac 40:00:22:AA:00:99
ESCON Add Virtual>lan tok
ESCON Add Virtual>maxdata 2052

(continue in same session with next row)


3


Devices
Channel Adapters
ESCON Interfaces
ESCON Subchannels


Interface 2, Base net 1, Protocol LSA
Device address: E4
Subchannel type: read/write
Link address: EF

ESCON Add Virtual>subchannel add
(cont'd)
ESCON Add LSA Subchannel>device E4
ESCON Add LSA Subchannel>link EF

(Type exit twice and then list all)



System
General


System name: NUA_SC1C
Location: XYZ
Contact: Admin

Config>set host
Config>set location
Config>set contact




System
SNMP Config
General


SNMP (checked)

Config>p snmp
SNMP Config>enable snmp



System
SNMP Config
Communities
General


Community name: admin
Access type: Read-write trap
Community view: All

SNMP Config>add community
SNMP Config>set comm access write


4


Protocols
IP
General


Internal address: 172.128.252.1
Router ID: 172.128.1.1

Config>p ip
IP config>set internal
IP config>set router-id



Protocols
IP
Interfaces


Interface 0 (TR slot 1 port 1)
IP address: 172.128.1.1
Subnet mask: 255.255.255.0

IP config>add address




Protocols
IP
OSPF
General


OSPF (checked)



Config>p ospf
OSPF Config>enable ospf


5


Protocols
IP
OSPF
Area Configuration
General


Area number: 0.0.0.0
Stub area (not checked)

OSPF Config>set area



Protocols
IP
OSPF
Interfaces


Interface 0
OSPF (checked)

OSPF Config>set interface
  Interface IP address  172.128.1.1
  Attaches to area 0.0.0.0

(Accept other defaults)



Protocols
DLSw
General
General


DLSw (checked)
SRB segment: FFD
Forward explorers: local TCP connection only

Config>p dls
DLSw Config>enable dls
DLSw Config>set srb
DLSw Config>enable forward local


6


Protocols
DLSw
General
Dynamic Neighbors


Dynamic neighbors (checked)

DLSw Config>enable dynamic


7


Protocols
DLSw
TCP Connections


(add)
Neighbor IP address: 172.128.252.1
(this is the router internal IP address)

DLSw Config>add tcp
  DLSw neighbor IP address: 172.128.252.1

(Accept other defaults)


8


Protocols
DLSw
Interfaces


Interface 0 (TR slot 1 port 1)
SAP type: SNA (SAPs 0,4,8,C)
Interface 2 (ESCON-LSA)
SAP type: SNA (SAPs 0,4,8,C)

DLSw Config>open 0 sna
DLSw Config>open 2 sna


9


Protocols
Bridging
General


General Tab:
Bridging (checked)
DLSw (checked)
SRB Tab:
Internal Virtual Segment: FF0

Config>p asrt
ASRT config>enable br
ASRT config>enable dls


10


Protocols
Bridging
Interfaces


Interface 0 (TR slot 1 port 1)
Bridging port (checked)
Interface supports: SRB
Segment number: 001
MTU size: 2052


('enable br' assumed)
ASRT config>disable transp 1
ASRT config>enable source 1


11

Notes:

  1. add dev defines a single port, not an adapter.

  2. The configuration program assigns an interface number to all ports of an adapter automatically and you delete the ones you do not want to use. From the command line, you type the add dev command for each port you want to use, and the interface number (also known as "net number") is the output of the command.

  3. The MAC address representing this LSA loopback interface is the target MAC address that all end stations in the DLSw network use to reach the host through this Network Utility.

  4. You need a write-capable SNMP community only if you want to download configuration files from the configuration program directly into the router. SNMP is not required to TFTP a configuration file to the router.

  5. You could choose to use RIP in place of OSPF.

  6. We enable local forwarding to allow end stations on the local campus to reach the host. We disable the forwarding of remote explorers as a general filter, to prevent backbone LAN traffic from generating DLSw search messages on the WAN links to remote sites. This means that all remote circuits must be initiated by the remote routers. If your network requires the host to be able to initiate connections out to the remote sites, change this parameter to "forward to all DLSw peers".

    If the remote routers are IBM routers, you can configure them individually to control which search messages they want to receive, using MAC address and NetBIOS name lists. You can also configure whether each will bring up its TCP connection to Network Utility all the time or drop it when unused, using the connectivity setup type parameter.

  7. Having dynamic neighbors enabled is the default value, so you do not have to change this panel or issue this command. We show it here to point out that this is the parameter that allows remote DLSw partners (neighbors) to establish TCP connections to this Network Utility without you having to define their IP addresses here. Each remote router needs to be configured with this Network Utility's internal IP address (172.128.252.1) as its partner address.

  8. Adding the internal IP address as a neighbor is required to enable DLSw to carry traffic from the ESCON/LSA interface to the backbone LAN.

  9. SAPs are opened on Interface 0 to enable the LLC flow to the local LAN switches, and are not required for remote DLSw to work.

  10. "enable br" automatically creates a TB bridge port for the token-ring interface. The bridge port number is 1, and is independent of adapter port numbers and box interface numbers.

  11. The disable and enable commands change bridge port 1 from TB to SRB. Bridging is required on this interface to support local end station traffic looping through DLSw from the Campus Backbone to the host.


[ Top of Page | Previous Page | Next Page | Table of Contents ]